Migrate applications to Arm servers using migrate-ease
Introduction
Assessing your code for migration to Arm
Migrate-ease and supported programming languages
Getting started with migrate-ease
Try it out
Next Steps
Migrate applications to Arm servers using migrate-ease
Who is this for?
This is an introductory topic for developers looking to migrate applications to Arm-based servers using migrate-ease, a code analysis tool that scans local source trees or Git repositories to identify architecture-specific porting issues before migration.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Identify architecture-specific dependencies in your application's source code.
- Recognize common migration challenges and how to resolve them.
- Use migrate-ease to detect and address AArch64 portability issues.
Prerequisites
Before starting, you will need the following:
- Access to an Arm-based instance for testing and validation.
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
migrate-ease analyzer. First, you’ll prepare a Linux environment, scan a local source tree or Git branch for AArch64 concerns, and generate a JSON report. Next, you’ll target Armv8-A and analyze an older Protobuf release to see how missing architecture support appears in the findings. You can then apply the same process before rebuilding and testing your own workloads on Arm servers.Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
x86_64 or Arm AArch64 Linux host to run the analysis.result.json, then review the report for AArch64 portability issues.--git-repo and --branch to analyze a specific repository and branch without cloning it first. The example targets Protobuf v2.5.0 to illustrate missing AArch64 support.migrate-ease against your existing local source tree or a Git repository.migrate-ease as a read-only analysis. It doesn’t change your source tree.